create - force --no-open when inside Posit Workbench#12967
Conversation
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) ✅ license/snyk check is complete. No issues have been found. (View Details) |
|
Tested manually on Posit workbench - No new window opened. |
jthomasmock
left a comment
There was a problem hiding this comment.
LGTM other than a minor nit about RStudio Workbench vs Posit Workbench.
| const allowPrompt = isInteractive && !!options.prompt && !options.json; | ||
|
|
||
| // Specific case where opening automatically in an editor is not allowed | ||
| if (options.open !== false && isRStudioWorkbench()) { |
There was a problem hiding this comment.
Minor nit and this might be an older boolean, but isPositWorkbench would be more appropriate.
There was a problem hiding this comment.
Yes this is an older function
quarto-cli/src/core/platform.ts
Lines 37 to 41 in 24e9355
I did not bother renaming, but I can for sure.
There was a problem hiding this comment.
Done in 18c12f5
Probably best to also change in quarto-dev/quarto ?
closes #12965
@jthomasmock, @MariaSemple, this is simple tweak to force
--no-openwhen inside workbench.I added info message in case a user is explicitly setting
--open <editor name>to explain this is not permitted.I'll manually test it somewhere I can access.
Is there any other specific behavior it should have in the Workbench context? Should we open automatically or prompt to open, but in a different way?
You can also test this PR by cloning, switching branch and installing from source Quarto dev version